Method and apparatus for providing data center functions for support of an electric vehicle based data center

ABSTRACT

In one embodiment, a method includes identifying a plurality of servers located in a plurality of electric vehicles, associating the servers with an electric vehicle based cloud data center, allocating resources to the servers in the electric vehicle based cloud data center to perform data center functions, and managing the servers in the electric vehicle based cloud data center.

STATEMENT OF RELATED APPLICATIONS

The present application is a continuation of U.S. Nonprovisional application Ser. No. 16/871,877, filed on May 11, 2020, which claims priority from U.S. Provisional Application No. 62/981,339, filed on Feb. 25, 2020, the contents of which are incorporated herein by reference in their entirety.

TECHNICAL FIELD

The present disclosure relates generally to data centers, and more particularly, to an electric vehicle based data center.

BACKGROUND

Data centers are very expensive to build and land for data centers is also expensive. Construction costs are often very high and permits may take years to obtain. Cooling costs and building maintenance costs are also high. Power distribution into and through the facility may be difficult to obtain and may not deliver full capacity operation. Server replacement and upgrades are often time consuming and require a significant amount of labor. Thus, start-up and maintenance costs for a very large data center may be prohibitive in many cases.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is an example of an electric vehicle based data center, in accordance with one embodiment.

FIG. 2A illustrates an example of cell tower zones in which one or more electric vehicles may be located.

FIG. 2B illustrates charging station locations relative to a cell tower zone.

FIG. 2C illustrates resource allocation zones, in accordance with one embodiment.

FIG. 3 illustrates details of a server appliance installed in the electric vehicle, in accordance with one embodiment.

FIG. 4 illustrates a server appliance rack installed in an electric truck, in accordance with one embodiment.

FIG. 5A illustrates the electric vehicle driving from a warm climate to a cold climate.

FIG. 5B is a graph illustrating an example of temperature distribution and active server count in the server appliance as the electric vehicle moves from the warm climate to the cold climate as shown in FIG. 5A.

FIG. 5C is a graph illustrating an example of power distribution and active server count in the server appliance.

FIG. 6A illustrates a mobile device running a map application located in the electric vehicle for use in identifying a trip distance for the electric vehicle.

FIG. 6B is a graph illustrating an example of active server count based on a distance to travel.

FIG. 7A illustrates an air inlet and fan for cooling the server appliance in the electric vehicle, in accordance with one embodiment,

FIG. 7B is a graph illustrating an example of fan power as a function of electric vehicle movement.

FIG. 8 illustrates a flow control damper for use in directing cooling air from different inlets to cool the server appliance, in accordance with one embodiment.

FIG. 9A is a block diagram of a cloud manager system for the electric vehicle based data center, in accordance with one embodiment.

FIG. 9B is a block diagram of another cloud manager system for the electric vehicle based data center, in accordance with another embodiment.

FIG. 9C is a block diagram of a zone cloud server in communication with a plurality of server appliances, in accordance with one embodiment.

FIG. 10 is a block diagram of a server appliance manager system for managing server appliances in multiple zones, in accordance with one embodiment.

FIG. 11 is a block diagram depicting an example of a network device that may be used to implement the embodiments described herein.

FIG. 12A is a flowchart illustrating an overview of a process for providing data center functions to support the electric vehicle based data center, in accordance with one embodiment.

FIG. 12B is a flowchart illustrating an overview of a process for identifying an electric vehicle operating environment and adjusting server resources based on the operating environment.

Corresponding reference characters indicate corresponding parts throughout the several views of the drawings.

DESCRIPTION OF EXAMPLE EMBODIMENTS Overview

In one embodiment, a method generally comprises identifying a plurality of servers located in a plurality of electric vehicles, associating the servers with an electric vehicle based cloud data center, allocating resources to the servers in the electric vehicle based cloud data center to perform data center functions, and managing the servers in the electric vehicle based cloud data center.

In another embodiment, a method generally comprises identifying an operating environment at an electric vehicle comprising a plurality of servers operable to perform data center functions in an electric vehicle based cloud data center comprising a plurality of electric vehicle servers, and adjusting server resources at the electric vehicle based on the operating environment.

In yet another embodiment, a server appliance generally comprises a plurality of servers, a router in communication with the servers, an electrical interface for receiving power from an electric vehicle battery, and a wireless interface for communication with an electric vehicle based cloud data center in which the servers are configured to operate, wherein the server appliance is configured for mounting in an electric vehicle and the electric vehicle based cloud data center comprises a plurality of electric vehicle servers mounted in a plurality of electric vehicles.

Further understanding of the features and advantages of the embodiments described herein may be realized by reference to the remaining portions of the specification and the attached drawings.

EXAMPLE EMBODIMENTS

The following description is presented to enable one of ordinary skill in the art to make and use the embodiments. Descriptions of specific embodiments and applications are provided only as examples, and various modifications will be readily apparent to those skilled in the art. The general principles described herein may be applied to other applications without departing from the scope of the embodiments. Thus, the embodiments are not to be limited to those shown, but are to be accorded the widest scope consistent with the principles and features described herein. For purpose of clarity, details relating to technical material that is known in the technical fields related to the embodiments have not been described in detail.

Data center costs are driven by power (required power, backup power, electrical and power distribution equipment), land and building costs (construction, maintenance, permits, taxes), cooling costs (cooling equipment and power to drive the cooling equipment), network connectivity (e.g., fiber optic connections), and repair, infrastructure maintenance, and upgrade costs. If a data center is placed in an electric vehicle, many of these requirements and costs may be eliminated. For example, use of an electric vehicle based data center in place of a conventional data center eliminates the cost of land, building infrastructure, local and backup power, and wiring and cabling costs for fixed server racks. Maintenance and server updates may be performed during regularly scheduled electric vehicle maintenance and software updates.

The embodiments described herein provide methods, systems, and apparatus for implementing an electric vehicle based data center. In one or more embodiments, one or more servers are placed along with a router and cellular/wireless system to transmit and receive data at an electric vehicle to create an electric vehicle based data center. In one or more embodiments, the server appliance is managed in a communications network (e.g., cloud based management system) as the electric vehicle moves or remains stationary. Resources (e.g., processing, storage) may be allocated based on location of the electric vehicles or density of the electric vehicles in a specified zone, for example. In one or more embodiments, server resources may be adjusted based on an operating environment of the electric vehicle, including for example, driving distance, zone operation, temperature (internal or external), power availability, electric vehicle usage, terrain elevation, vehicle loading, projected usage, or any combination of these or other variables. The electric vehicle based data center allows for the electric vehicle owner to maintain the servers, provide power, and upgrade the server appliance. Land and construction costs are eliminated and minimal costs are built into the electric vehicle. The electric vehicle based data center eliminates the need for a conventional fixed (stationary) data center and makes the data center servers fully mobile.

As described in detail below, one or more embodiments provide a method and apparatus for incorporating control, power, cooling, security, and communications to support the electric vehicle based data center. The adaptation of power, cooling, and communications for data center usage are performed in conjunction with basic functions that are needed in an electric vehicle. In one or more embodiments, a control system manages limited resources and assigns resources to fill appropriate needs at any given time, environment, or operational needs of the electric vehicle. In one or more embodiments, system functionality covers power load shedding that allows the electric vehicle to have the power needed for its original purpose, while the data center is a secondary function.

In one or more embodiments, a method for providing data center functions for support of an electric vehicle based cloud data center includes identifying servers located in electric vehicles, associating the servers with the electric vehicle based cloud data center, allocating resources to the servers in the electric vehicle based cloud data center to perform data center functions, and managing the servers in the electric vehicle based cloud data center. As described below, identification of electric vehicle servers for resource allocation may be based on an estimated number of electric vehicles in a zone or region. One or more cloud managers may be used to associate the servers with the electric vehicle based cloud data center (e.g., perform network communications therewith), allocate resources, and manage the servers (e.g., move resources between servers).

Referring now to the drawings, and first to FIG. 1 , an electric vehicle (EV) based cloud data center 17 (also referred to herein as an electric vehicle based data center or an electric vehicle based cloud managed data center), is shown in accordance with one embodiment. One or more servers (server blades) are located in an electric vehicle (car 10, truck 12) and interface with a cell tower 14 (e.g., 4G, 5G tower point) through an antenna 15. The server (or servers) and associated components (e.g., router and wireless module described below with respect to FIG. 3 ) are referred to herein as a server appliance 16 and may be installed in any suitable location within the electric vehicle 10, 12. As described below with respect to FIG. 4 , the truck 12 may comprise a plurality of server appliances 16 in a server appliance rack. The electric vehicle based cloud data center 17 is managed by a server appliance cloud manager 18. As described in detail below with respect to FIG. 10 , the server appliance cloud manager 18 may comprise any number of components such as zone managers or regional managers that may communicate with a central office. As shown in FIG. 1 , one or more of the electric vehicles may also be in communication with the server appliance cloud manager 18 through Wi-Fi 19 (e.g., outdoor Wi-Fi or other access point (AP) in Wi-Fi network).

The server appliance cloud manager operates 18 in the electric vehicle based cloud managed data center 17, which distributes data center functions (e.g., collecting, storing, processing, distributing, or allowing access to data) to a plurality of servers (in server appliances 16) located in a plurality of electric vehicles 10, 12. The electric vehicle based data center 17 may provide services including, for example, data storage, data backup and recovery, data processing, data management, data networking, and other services. As described below, the electric vehicle based cloud managed data center 17 allocates resources (e.g., processing, memory, local storage, services, network connectivity, or other computing resources) to the servers within the server appliances 16 and may utilize, for example, virtual machines to move resources between servers, microservices for applications, orchestration to manage applications, or any other virtualization tools or virtualized infrastructure that supports applications and workloads across the physical servers and into a cloud environment.

The electric vehicle based cloud data center 17 may provide data functions to support and operate as an enterprise data center, hyperscale data center, telecom data center, managed services data center, or any other type of data center. The electric vehicle based data center 17 may include any number of servers (e.g., 500, 1,000, 5,000, 10,000, >10,000, or any other number of servers).

It is to be understood that the network shown in FIG. 1 is a simplified schematic and the network may include any number of server appliances 16 located in any number of electric vehicles 10, 12 in wireless communication over any number of cell towers 14, Wi-Fi networks 19, or other wireless communication stations. Furthermore, the electric vehicles 10, 12 shown in FIG. 1 are only examples and any type of electric vehicle may be used with one or more server appliances positioned in any suitable location within the vehicle. The antenna 15 extending from the vehicles 10, 12 as illustrated in FIG. 1 is shown to depict wireless transmission. As is well known by those skilled in the art, the antenna may be positioned in any location on the vehicle (e.g., trace on window). Also, while a box located towards a front end of the vehicle 10, 12 is shown to depict the server appliance 16, it is to be understood that the server appliance may be cubic or any other suitable shape to allow space for other needs or functions of the electric vehicle and may be positioned in any location in which sufficient space is available in the electric vehicle. The server appliance 16 may also be configured such that servers or server appliances may be easily added or removed depending on space availability within the electric vehicle for applications such as the truck 12 in which available space may vary depending on the usage. The server appliance 16 may be modular, customer maintained, operable with low power usage, and easily upgraded.

As a result of the server appliances 16 being mobile, the number of available servers in a specified cell range or zone may vary over time. As described below, calculations may be performed to determine available servers in a specified cell tower range at any given time and server loading zones, for which processing may be moved to, may be identified. The following describes example calculations for use in allocating resources among servers within the electric vehicle based cloud managed data center 17.

Electric vehicles such as cars 10 typically remain within a particular region or zone (e.g., residential neighborhood, geographical region surrounding home and work or home and school). It is therefore possible to predict server density within a zone. FIG. 2A illustrates an example of cell towers (cell 1, cell 2, cell 3), each having a specified range defined by circles 20 a (for cell 1), 20 b (for cell 2), 20 c (for cell 3), and 20 d (for cell N). Each cellular zone 20 a, 20 b, 20 c, 20 d is located in one or more regional zones (zone 1, zone, zone 3), which includes overlapping cell tower coverage. Each cell tower may be in more than one zone and each zone may include any number of cell towers. As shown in the example of FIG. 2A, zone 2 includes zone 1, and zone 3 includes zone 1 and zone 2. It is to be understood that FIG. 2A is only an example and each regional zone may include any number of cell towers.

As previously noted, most electric cars stay within a geographical region. In one example, X₁% of all electric vehicles in zone 1 may remain in that zone at least 95% of the time. Similarly, 99% of the electric vehicles may remain in zone 2 and 99.9% of the electric vehicles remain in zone 3, for example. At any given time, there would be X N % of electric vehicles with servers in a zone N, which would provide a reliable load distribution in clusters for a cell tower.

In one example, the placement of servers or electric vehicle density may be determined by the availability of charging points within a cellular zone. For example, as shown in FIG. 2B, a cell tower coverage area 22 includes N charging stations (C₁, C₂, CN), with charging station C₃ located just outside of its coverage area 22.

In one or more embodiments, resources may be allocated to a plurality of resource zones (zone 1, zone 2, zone 3, zone 4, zone N) based on the number of charging stations in the resource zone (FIG. 2C). In one example, Y N represents the number of charging stations and the probability (P) of keeping electric vehicles in the zone may be expressed as:

P=[1−Y/Y _(N)]

-   -   Wherein:     -   Y is the number of charging stations in use; and     -   Y N is the total number of charging stations in a zone.         The fewer and more powerful charging stations may drive the         greatest density of electric vehicles in a cellular zone (or         zones).

In one or more embodiments, resources (e.g., storage and processing resources) may be allocated to the servers located in the zone with overlap 24 between the zones taken into account. In one example, a percentage of resources (Z₃) to be allocated in zone 3 of FIG. 2C may be calculated as follows:

$Z_{3} = {\left\lbrack {\sum\limits_{1}^{4}\left( {16\%} \right)} \right\rbrack_{\max} + \left\lbrack {100 - {16\% \times \left( {4{zones}} \right)}} \right\rbrack_{\min}}$ $\begin{matrix} {Z_{N} = {{100} - \left( {16} \right)_{overlap}}} \\ {{for}{each}{{overlap}.}} \end{matrix}$

In the above example, the percentage of resource allocation for zone 3 is based on a 16% overlap with each of the other four zones (Z₁, Z₂, Z₄, Z_(N)). It is to be understood that this is only an example and a different number of zones or percentage overlap may be used.

In one or more embodiments, initial calculations may be used to estimate a server density and machine learning may be used to determine available electric vehicle resources and update the calculations over time.

Referring now to FIG. 3 , a block diagram illustrating components of the server appliance 16 is shown in accordance with one embodiment. The server appliance 16 may be in wireless communication with the cell tower 14 or Wi-Fi device 19, as previously described (FIGS. 1 and 3 ). The server appliance 16 may include, for example, one or more servers 30 (server₁, server₂, . . . server_(N)) in communication with a router 32. The router 32 is in communication with a wireless module (interface) (e.g., cellular module 36 (e.g., 4G/5G), Wi-Fi module 38) for communication with the electric vehicle based cloud data center in which the servers 30 are configured to operate. The server appliance 16 further includes an electrical interface (power interface) 34 for receiving power from the electric vehicle (EV) battery. In the example shown in FIG. 3 , power is received at the router 32, which distributes power to the other components. Power may be delivered, for example, as PoE (Power over Ethernet) or ESP (Extended Safe Power)/FMP (Fault Managed Power) (pulse power or multi-phase pulse power with safety features) as described in U.S. patent application Ser. No. 16/671,508 (“Initialization and Synchronization for Pulse Power in a Network System”), filed Nov. 1, 2019.

The server appliance 16 is contained within a housing 35 configured for mounting in the electric vehicle 10. As previously described, the housing 35 may be any shape suitable to fit within available space in the car, preferably without significant impact to operating features of the electric vehicle (e.g., trunk space, vehicle weight). As described below with respect to FIG. 4 , the housing for one or more server appliances in a truck may be referred to as a server appliance rack. The server appliance or server appliance rack is preferably configured for ease of installment, modification (e.g., changing number of servers or server appliances based on space availability), or server maintenance or upgrade. The housing 35 may be configured for receiving cooling air through an air inlet or fan, as described below with respect to FIGS. 7A and 8 .

It is to be understood that the term ‘server appliance’ as used herein may refer to any type of structure comprising multiple servers (server blades) and related components and configured for mounting in an electric vehicle.

FIG. 4 illustrates an example of the electric truck 12 that may be used in local areas or interstate trucking. The electric truck 12 may include a server appliance rack 40 comprising a plurality of servers managed as a group. For truck applications, servers may be organized in a ten piece server group 42 (or other size group) with independent cellular and Wi-Fi transceivers, for example. This allows for independent updates of each server group (appliance) 42. For short haul, resource allocation for servers in a truck may be handled as described above for local electric vehicles. For long haul, resource allocation may be downloaded at the start of computation and uploaded to the cloud manager at a new location.

Servers or server appliances may be powered down when not in use. Electric vehicle owners may also modify server usage. For example, an electric vehicle owner may allocate energy based on expected future driving. In one or more embodiments, the owner may deny use of servers during a long trip to conserve battery power. For short trips, full use of servers may be permitted. In another example, active server count may be reduced upon leaving a zone or based on battery life and battery temperature. As described below, a controller at the server appliance may automatically adjust server resources (active server count) based on an operating environment of the electric vehicle.

In one or more embodiments, a method for managing the servers at the electric vehicle may include identifying an operating environment at the electric vehicle and adjusting server resources at the electric vehicle based on the operating environment. For example, server usage may be adjusted based on driving distance, driving terrain or conditions, temperature (internal to or outside of the electric vehicle), available power, server power requirements, server type, or any combination of these or other factors. Adjustment of server resources may include reducing or increasing a number of active servers at the electric vehicle.

In one or more embodiments, server appliance load may be shed (number of active servers reduced) based on driving conditions and location. For example, as described below, server load may need to be adjusted to account for temperature changes based on location of the electric vehicle or temperature at the battery or server. Also, based on driving conditions, the electric vehicle may need more power for its driving functions (e.g., based on estimated trip distance, driver performance (habits), changes in terrain or grade of road, elevation change, electric vehicle weight, vehicle loading), thereby leaving less power available for data center functions. Monitoring of these factors or other factors along with modification of data center functions allow the electric vehicle to support the data center while still operating as an electric vehicle without any significant impact to performance of the electric vehicle.

As illustrated in FIG. 5A, an electric vehicle 50 with a data center server appliance may travel from a warm climate to a cold climate (or vice versa). FIGS. 5B and 5C illustrate examples of temperature and power distribution, respectively, for the electric vehicle. FIG. 5B is a graph, generally indicated at 52, showing an example of active server count versus relative temperature (hot, normal, cold). During normal temperature operation, all ten servers may be in operation. The graph may be, for example, a probability density function (PDF). During hot or cold operating conditions, the server count may need to be reduced due to impact to power availability. The temperature at which servers may be turned off or turned on may be predefined or may be a relative temperature based on typical local temperature of the location where the vehicle spends a greatest percentage of time. FIG. 5C is a graph, generally indicated at 54, showing an example of active server count versus percentage available power at the electric vehicle battery. As the percentage of available power drops off, the server count is reduced. In one or more embodiments, machine learning may be used to identify an optimum shutdown point for active servers in a server appliance based on power and temperature derating, as indicated by the X on the graphs of FIGS. 5B and 5C.

As previously noted, server derating (reducing active number of servers) may also be performed based on distance to travel. As shown in FIG. 6A, a mobile device 60 (e.g., cellular phone, tablet, laptop, GPS (Global Positioning System)/direction system integrated into the electric vehicle, and the like) may be located within the electric vehicle 10. The mobile device 60 may be coupled to the car (e.g., with USB or wireless connection 62 or integrated directly into the electric vehicle). The mobile device 60 may be running a map (directions application) (or similar software) that may be used to indicate distance to travel. FIG. 6B is a graph, generally indicated at 64, showing an example of active server count versus distance to travel. As the distance to travel increases, the server count may be reduced to save power needed for the trip. The distance may be predefined, configured based on usage patterns, or user defined.

It is to be understood that the operating environments described herein are only examples and any number or type of conditions or factors may be used to determine when to turn off or turn on one or more of the servers in the server appliance. For example, active server count in the server appliance may be adjusted based on one or more of outside temperature, battery temperature, available power, driving distance/terrain/elevation changes, driver habits (performance), server temperature, server power requirements, number of servers required, server type/style, vehicle loading, or any combination of these or other factors. The server appliance may communicate any changes in server resources (change in number of active servers at the server appliance) to the cloud manager so that the cloud manager may reallocate resources.

In one or more embodiments, the server appliance 16 may be positioned in the electric vehicle 10 such that air flow passes through the server appliance while the electric vehicle is in motion, as shown in FIG. 7A. A fan tray 70 (comprising one or more fans and a fan controller) may be positioned adjacent to the server appliance 16. Cooling air is received from an air inlet 72 and exits through an air outlet 74. One or more of the fans may be turned off while the electric vehicle 10 is moving with cooling air passing through the electric vehicle. The fans may be turned on for stationary operation as needed.

FIG. 7B is a graph, generally indicated at 76, illustrating an example of fan power usage versus electric vehicle movement (miles per hour). Fan speed may be adjusted based on temperature and vehicle movement. The dashed line 78 illustrates a simple slope and the solid line 79 shows a complex slope (e.g., hex). The relationship may also be expressed as an algebraic function. As the electric vehicle speed increases, the amount of fan power needed is reduced.

In a parked state, the air temperature under the electric vehicle is typically cooler. In one or more embodiments, a secondary air inlet 80 may be positioned to receive cooler air from an underside of the car 10, as shown in FIG. 8 . A flow control damper 82 may be used to divert air to the fan from the air inlet 72, air inlet 80, or a combination thereof based on speed of the car 10. For example, high speed air may open the damper 82 to the air inlet 72 from the front of the electric vehicle 10 to allow high velocity air cooling from the front of the car. When the electric vehicle is in a stationary position, the damper 82 may automatically divert to the under car inlet 80, as this air is typically cooler. The damper 82 may close the front air inlet 72 in stationary mode. In another example, inlet 80 may be used to provide both forced air cooling and under-side cooler air. In one or more embodiments, cooling resources from the electric vehicle may also be used when the electric vehicle is stationary or in motion.

As previously noted, a cloud manager within the electric vehicle based cloud managed data center is used to manage the server appliances at the electric vehicles. As described below with respect to FIGS. 9A-10 , the management functions may be distributed across any number of zone or regional cloud managers.

FIG. 9A illustrates a cloud manager implementation for managing the electric vehicle based data center, in accordance with one embodiment. As shown in the example of FIG. 9A, the cell tower 14 comprises a remote radio head (RRH) 90, which is in communication with a front haul router 92 and a zone cloud manager 94. The remote radio head 90 provides the RF (Radio Frequency) circuit of the base station at the cell tower 14. The front haul router 92 is in communication with the remote radio head 90 and provides high-speed forwarding to meet radio transport requirements for radio access network operation. Any number of zone cloud managers 94 may be in communication with a regional cloud manger 96, as described below with respect to FIG. 10 . In the example of FIG. 9A, there are two paths. A first path extends from the remote radio head 90 to the front haul router 92, to a back haul router 98, and to a central office. A second path extends from the remote radio head 90 to the zone cloud manager 94, to the regional cloud manager 96, and then to a SAM (Server Appliance Manager) at the central office. The cloud managers 94, 96 may be remotely located.

FIG. 9B illustrates an alternative to the configuration shown in FIG. 9A in which an off-load engine is used for the server appliance zone manager 94 and regional cloud manager 96. In this example, the zone cloud manager 94 comprises an off-load API (Application Programming Interface) or service blade working with the front haul router 92. The regional cloud manager 96 also comprises an off-load API or service blade function working with the back haul router 98, which is in communication with the service appliance manager at the central office.

It is to be understood that the communication paths and components shown in FIGS. 9A and 9B are only examples and other components or arrangements may be used without departing from the scope of the embodiments.

As previously described, each zone may comprise any number of server appliances at any point in time. FIG. 9C illustrates an example of a zone cloud server 99 in communication with a plurality of server appliances 16 (1 . . . N). In one example, each server appliance 16 comprises 10 servers. If N=100 electric vehicles with each electric vehicle comprising one server appliance with 10 servers, the total number of servers is one thousand. Thus, if there are one hundred electric vehicles within a zone, it is possible for one thousand dedicated servers to exist within a twenty-four hour period, for example. As previously noted, the electric vehicle based cloud data center may comprise any number of servers, which may change over time. For example, if a large number of trucks are located in a zone, the data center may comprise a greater number of servers. In one example, the electric vehicle based data center comprises at least one thousand servers.

In one example, 100 kWh is provided in a typical electric vehicle and cooling of ten servers is reasonable. Since electric vehicle charging costs are low and servers are owner maintained (e.g., owner upgraded or upgraded during maintenance interval by service personnel), it would not be difficult to send ten new model servers out for an electric vehicle owner to easily upgrade and the costs to maintain ten servers in an electric vehicle would be relatively low. It is to be understood that the number of servers in a server appliance, the number of service appliances in an electric vehicle, and the number of server appliances in a zone as described herein are only examples and a different number of servers or server appliances may be used, without departing from the scope of the embodiments.

FIG. 10 illustrates an example of a server appliance cloud manager 100 for multiple zones 102 (zone 1 . . . zone N), in accordance with one embodiment. Each zone 102 includes a plurality of server appliances (SA) 16 in wireless communication with the cell tower 14. The remote radio head (RRH) 90 at the cell tower 14 is in communication with a front haul router (FHR) 92, as previously described. A server appliance zone manager (SAZM) 104 is in bidirectional communication with the front haul router 92. A back haul router (BHR) 98 communicates with the front haul routers 92 in different zones 102 and is also in communication with a regional server appliance zone manager (RSAZM) 106. The back haul router 98 communicates with a central office 108, which is in communication with a server appliance manager (SAM) 110. Each of the zones 102 may include any number of server appliances 16 and there may be any number of zones in communication with the back haul router 98 (back haul router region). There may be any number of back haul router regions in communication with the central office 108.

The server appliance zone manager 104 handles cloud coordination within a specific cell or wireless zone 102. The regional server appliance zone manager 106 handles cloud coordination data handoff between servers (server appliances 16) in one cell area or wireless zone 102 transferring data to servers in another cell area or zone. The server appliance manager 110 is essentially a master cloud coordinator for all servers within its cloud server domain. There may be multiple cloud server domains, logically isolated (or not isolated) from each other. The domains may be physically isolated based on zone or region demand, for example.

FIG. 11 illustrates an example of a network device 111 (server appliance) that may be used to implement one or more embodiments described herein. In one or more embodiments, the network device 111 is a programmable machine that may be implemented in hardware, software, or any combination thereof. The network device 111 includes one or more processor 112 (e.g., hardware/processor), memory 113 (local or cloud storage), wireless interface 114, and software 115 (e.g., controller, authentication software, logic, microprocessor).

Memory 113 (local or cloud storage) may be a volatile memory or non-volatile storage, which stores various applications, operating systems, modules, and data for execution and use by the processor 112. The network device 111 may include any number of memory components.

Logic (software, firmware, control logic, code) may be encoded in one or more tangible media for execution by the processor 112. For example, the processor 112 may execute codes stored in a computer-readable medium such as memory 113. The computer-readable medium may be, for example, electronic (e.g., RAM (random access memory), ROM (read-only memory), EPROM (erasable programmable read-only memory)), magnetic, optical (e.g., CD, DVD), electromagnetic, semiconductor technology, or any other suitable medium. In one example, the computer-readable medium comprises a non-transitory computer-readable medium. The network device 111 may include any number of processors 112 or microprocessors. In one or more embodiments, components of the network device 111 may be configured to implement processes described below with respect to flowcharts of FIGS. 12A and 12B.

The network device 111 further includes one or more power interface 119 (e.g., primary, backup) to provide power to the server appliance from the electric vehicle battery. Power may be delivered directly from the battery or may be modified for delivery as PoE, ESP/FMP as previously described.

As shown in FIG. 11 , the network device 111 may include one or more components to address security aspects. For example, the network device 111 may include a communications module 116 comprising one or more security features, hardware/software trust authentication module 117, and a tamper resistant device or mechanism 118.

It is to be understood that the network device 111 shown in FIG. 11 and described above is only an example and that different configurations of devices (with more or fewer components) may be used. For example, the network device 111 may further include any suitable combination of hardware, software, algorithms, processors, devices, components, or elements operable to facilitate the capabilities described herein.

FIG. 12A is a flowchart illustrating an overview of a process for supporting data center functions in the electric vehicle based cloud data center, in accordance with one embodiment. Servers located in the electric vehicles are identified at step 120. As previously described, this may comprise estimating a number of electric vehicles in a zone based on charging stations within the zone, for example. The servers are associated with the electric vehicle based cloud data center (step 122). As previously described, a data center zone cloud manager or zone cloud server may communicate with the servers located in the zone to associate the servers with the data center. Resources are then allocated to the servers to perform data center functions (step 124). The servers are managed at the electric vehicle based cloud data center (step 125), which may include reallocating resources as server resources at the electric vehicles change or electric vehicles move between zones. For example, the servers may be managed by the zone cloud manager, which is in turn managed by the regional cloud manager.

FIG. 12B is a flowchart illustrating an overview of a process for adjusting server appliance operation based on an operating environment at the electric vehicle, in accordance with one embodiment. A vehicle operating environment (e.g., temperature, driving distance, available power, etc.) is identified at step 126. Server resources at the server appliance are adjusted (e.g., one or more servers turned on or off) as needed (step 128). As previously described with respect to FIGS. 5A-6B, active server count may be adjusted based on climate, expected driving distance, or any other factors.

It is to be understood that the processes shown in FIGS. 12A and 12B are only examples and that steps may be added or modified without departing from the scope of the embodiments.

As can be observed from the foregoing, one or more embodiments, which include incorporation of a server (e.g., server blade set) into an electric vehicle, are particularly advantageous in that they eliminate costs associated with conventional data centers including, for example, cost of land and building infrastructure, power requirements, back-up power generation, maintenance server updates, and wiring and cabling costs for a large number of server racks.

Although the method and apparatus have been described in accordance with the embodiments shown, one of ordinary skill in the art will readily recognize that there could be variations made without departing from the scope of the embodiments. Accordingly, it is intended that all matter contained in the above description and shown in the accompanying drawings shall be interpreted as illustrative and not in a limiting sense. 

What is claimed is:
 1. A method comprising: identifying a plurality of servers located in a plurality of electric vehicles; associating said plurality of servers with an electric vehicle based cloud data center; allocating resources to said plurality of servers in the electric vehicle based cloud data center to perform data center functions, wherein allocating resources comprises calculating a percentage of the resources to allocate to said plurality of servers in a zone of a plurality of zones, wherein calculating said percentage of resources takes into account an overlap of the zone with other zones of the plurality of zones; and managing said plurality of servers in the electric vehicle based cloud data center.
 2. The method of claim 1, further comprising estimating a server density within the zone based on a number of electric vehicle charging stations within the zone.
 3. The method of claim 1, wherein managing said plurality of servers comprises reallocating resources to one or more of said plurality of servers within the zone in the electric vehicle based cloud data center as server resources change at the electric vehicles within the zone or as the electric vehicles move between zones of the plurality of zones.
 4. The method of claim 1, wherein each of the electric vehicles comprises a server appliance comprising at least two of the servers, a router, and a wireless module for communicating with the electric vehicle based cloud data center.
 5. The method of claim 1, wherein managing said plurality of servers comprises managing the servers within a zone at a zone cloud manager and coordinating data handoff between said plurality of servers in different zones at a regional cloud manager.
 6. A method comprising: identifying a plurality of servers located in a plurality of electric vehicles; associating said plurality of servers with an electric vehicle based cloud data center; allocating resources to said plurality of servers in the electric vehicle based cloud data center to perform data center functions; and managing said plurality of servers in the electric vehicle based cloud data center, wherein managing said plurality of servers comprises managing the servers within a zone of a plurality of zones at a zone cloud manager and coordinating data handoff between said plurality of servers in different zones of the plurality of zones at a regional cloud manager.
 7. The method of claim 6, further comprising: estimating a server density within the zone based on a number of electric vehicle charging stations within the zone; and allocating the resources to said plurality of servers in the electric vehicle based cloud data center based on the server density within the zone.
 8. The method of claim 6, wherein allocating the resources comprises calculating a percentage of the resources to allocate to said plurality of servers in the zone, wherein calculating said percentage of resources takes into account overlap of the zone with other zones of the plurality of zones.
 9. The method of claim 6, wherein each of the electric vehicles comprises a server appliance comprising at least two of the servers, a router, and a wireless module for communicating with the electric vehicle based cloud data center.
 10. The method of claim 6, wherein managing said plurality of servers further comprises reallocating resources to one or more of said plurality of servers within the zone in the electric vehicle based cloud data center as server resources change at the electric vehicles within the zone or as the electric vehicles move between zones of the plurality of zones.
 11. A server appliance comprising: a plurality of servers; a router in communication with said plurality of servers; an electrical interface for receiving power from an electric vehicle battery; and a wireless interface for communication with an electric vehicle based cloud data center in which the servers are configured to operate, wherein the server appliance is configured for mounting in an electric vehicle and the electric vehicle based cloud data center comprises a plurality of electric vehicle servers mounted in a plurality of electric vehicles, wherein resources are allocated to said plurality of servers of the server appliance to perform data center functions, and said plurality of electric vehicle servers are managed by a server appliance cloud management system in the electric vehicle based cloud data center.
 12. The server appliance of claim 11, further comprising: a controller configured to adjust server resources at the electric vehicle based on an operating environment of the electric vehicle.
 13. The server appliance of claim 12, wherein the controller is configured to reduce or increase a number of active servers at the electric vehicle based on at least one of a location of the electric vehicle and/or driving conditions at the electric vehicle.
 14. The server appliance of claim 12, wherein the controller is configured to reduce or increase a number of active servers at the electric vehicle based on at least one of an operating temperature at the electric vehicle and/or available power at the electric vehicle battery.
 15. The server appliance of claim 11, wherein the server appliance comprises at least ten servers and wherein the electric vehicle based cloud data center comprises at least one thousand of the electric vehicle servers.
 16. The server appliance of claim 11, wherein the electric vehicle comprises a truck and the server appliance is configured for operation with a managed group of server appliances at the truck.
 17. The server appliance of claim 11, further comprising an electric vehicle mounted fan for cooling the electric vehicle servers and a fan controller for adjusting a fan speed based on movement of the electric vehicle.
 18. The server appliance of claim 11, wherein the server appliance is configured for receiving cooling air from an air inlet positioned to receive air from an underside of the electric vehicle.
 19. The server appliance of claim 11, further comprising an authentication module for communications security.
 20. The server appliance of claim 11, further comprising a tamper resistant device for protecting the server appliance. 